Capability exposure implementation method and system, and related device

ABSTRACT

A capability exposure implementation method and system, and a related device are provided. A method embodiment of the present disclosure includes: obtaining capability information of a radio access network device, configuring an API, and setting a use time limit of the API, where the API is used to provide the capability information for a second mobile edge platform; triggering a registration function to send registration information to the second mobile edge platform, where the registration information includes an identifier of the API; receiving an API request sent by the second mobile edge platform, where the API request includes the identifier of the API; detecting whether the use time limit of the API expires; and if the use time limit of the API does not expire, sending an API response to the second mobile edge platform by using the API, where the API response includes the capability information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2015/095940, filed on Nov. 30, 2015, the disclosure of which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present invention relates to the field of wireless communicationstechnologies, and specifically, to a capability exposure implementationmethod and system, and a related device.

BACKGROUND

A Mobile Edge Computing (MEC) server provides an information technology(IT) service environment and a cloud computing capability on a radioaccess network (RAN) close to a mobile subscriber, and creates a highlydistributed environment for deploying applications and services. FIG. 1is a schematic diagram of an application of an MEC server in the priorart. In FIG. 1, the MEC server includes an underlying infrastructure, amobile edge platform, and an edge service server. The underlyinginfrastructure includes an MEC hardware resource layer and an MECvirtualization layer. The mobile edge platform is a core of the MECserver, and includes an MEC virtual management layer (for example, IaaS)and an MEC application service platform. A location of the MEC virtualmanagement layer is selectable, and the MEC virtual management layer maybe located at another location and is not implemented on the mobile edgeplatform. The MEC application service platform is configured to providea data routing (Traffic Offload Function, TOF for short) service, aradio network information service (RNIS), a communication service, aregistration service, and the like. On the mobile edge platform, aregistration service module exposes the TOF service, the RNIS, and thelike to an MEC application (Application, APP for short) program in avirtual machine (Virtual Machine, VM for short) of the edge serviceserver for use.

Currently, a location of an MEC server is mostly considered duringdeployment of the MEC server. For example, there are three deploymentscenarios in the prior art: In a first deployment scenario, the MECserver is deployed on an eNodeB side of Long Term Evolution (LTE), andone MEC server is deployed on one eNodeB side; in a second deploymentscenario, the MEC server is deployed on a convergence node of LTE or3^(rd) Generation (The 3rd Generation Telecommunication, 3G for short),and a plurality of base stations may share one MEC server; in a thirddeployment scenario, the MEC server is deployed on a 3G radio networkcontroller (RNC), and a plurality of base stations may share one MECserver. The MEC servers in the first deployment scenario and the thirddeployment scenario are deployed on a radio access network side, so asto reduce a delay, optimize system performance, and improve quality ofexperience (QoE) of a user. The MEC server in the second deploymentscenario is deployed on an upper-layer node of a radio access network,for example, a 3G convergence node, so as to support mobility. However,because only the location of the MEC server is considered in theforegoing three deployment manners, the deployment manners are notsufficiently flexible, and development and application of the MEC serverare limited.

SUMMARY

Based on the foregoing descriptions, the present invention provides acapability exposure implementation method and system, and a relateddevice, so as to implement more flexible deployment of an MEC server,and improve system performance.

A first aspect of the present invention provides a capability exposureimplementation method, where the method may include:

obtaining, by a first mobile edge platform, capability information of aradio access network device, configuring an application programminginterface API, and setting a use time limit of the API, where the API isused by the first mobile edge platform to provide the capabilityinformation for a second mobile edge platform;

triggering, by the first mobile edge platform, a registration functionto send registration information to the second mobile edge platform,where the registration information includes an identifier of the API;

receiving, by the first mobile edge platform, an API request sent by thesecond mobile edge platform, where the API request includes theidentifier of the API, and the API request is used to request thecapability information from the first mobile edge platform;

detecting, by the first mobile edge platform, whether the use time limitof the API expires; and

if the use time limit of the API does not expire, sending, by the firstmobile edge platform, an API response to the second mobile edge platformby using the API, where the API response includes the capabilityinformation.

It can be learned that, in the first aspect of the present invention,deployment of cascaded mobile edge platforms is implemented(specifically implemented by deploying cascaded MEC servers), and thecascaded mobile edge platforms include the first mobile edge platformdisposed on a radio access network side and the second mobile edgeplatform disposed on an upper-layer node of the radio access network.Based on the first mobile edge platform and the second mobile edgeplatform that are cascaded, because the first mobile edge platform isclose to the radio access network device, the first mobile edge platformcan obtain and store the capability information of the radio accessnetwork device. Then, the first mobile edge platform triggers theregistration function to provide the capability information of the radioaccess network device for the second mobile edge platform (specifically,the first mobile edge platform provides the capability information ofthe radio access network device for the second mobile edge platform byusing the API), so as to improve system performance and implementflexible service deployment, in addition to reducing processing load ofthe radio access network device.

Optionally, the capability information includes a channel signal state,cell load, terminal location information, network congestion, and aterminal identity.

Optionally, the identifier of the API may be a uniform resource locator(URL) or a uniform resource identifier (URI).

In some embodiments of the present invention, the capability exposureimplementation method provided in the first aspect further includes: ifthe use time limit of the API expires, obtaining, by the first mobileedge platform, current capability information of the radio accessnetwork device, where the current capability information is capabilityinformation of the radio access network device at a current time; andresetting, by the first mobile edge platform, the use time limit of theAPI, and sending, by using the API, an API response including thecurrent capability information to the second mobile edge platform.

In some embodiments of the present invention, the triggering, by thefirst mobile edge platform, a registration function to send registrationinformation to the second mobile edge platform includes: sending, by thefirst mobile edge platform, the registration information to the secondmobile edge platform.

In some embodiments of the present invention, the triggering, by thefirst mobile edge platform, a registration function to send registrationinformation to the second mobile edge platform includes: triggering, bythe first mobile edge platform, a management network element to send theregistration information to the second mobile edge platform by using themanagement network element.

In some embodiments of the present invention, the capability exposureimplementation method provided in the first aspect further includes:providing, by the first mobile edge platform, the capability informationfor a first edge service server by using the API, where the first edgeservice server and the first mobile edge platform are disposed in afirst Mobile Edge Computing MEC server.

A second aspect of the present invention provides a capability exposureimplementation method, where the method may include:

receiving, by a second mobile edge platform, registration information,where the registration information includes an identifier of anapplication programming interface API, the API is used by a first mobileedge platform to provide capability information for the second mobileedge platform, and the capability information is capability informationof a radio access network device;

sending, by the second mobile edge platform, an API request to the firstmobile edge platform, where the API request includes the identifier ofthe API, and the API request is used to request the capabilityinformation from the first mobile edge platform; and

receiving, by the second mobile edge platform, an API response sent bythe first mobile edge platform, where the API response includes thecapability information.

It can be learned that, based on the cascaded mobile edge platformsdescribed in the first aspect, after receiving the registrationinformation, the second mobile edge platform requests, by sending an APIrequest including the identifier that is of the API and that is in theregistration information, the first mobile edge platform to obtain thecapability information of the radio access network device, so as toshare processing load of the radio access network device, improve systemperformance, and promote an application scope of the mobile edgeplatform (or an MEC server).

Optionally, the capability information includes a channel signal state,cell load, terminal location information, network congestion, and aterminal identity.

In some embodiments of the present invention, before the sending, by thesecond mobile edge platform, an API request to the first mobile edgeplatform, the method includes: receiving, by the second mobile edgeplatform, a trigger request sent by a second edge service server, wherethe trigger request includes an identity ID of the radio access networkdevice and/or an ID of the first mobile edge platform, the triggerrequest is used to trigger the second mobile edge platform to send theAPI request to the first mobile edge platform, and the second edgeservice server and the second mobile edge platform are disposed in asecond Mobile Edge Computing MEC server; and determining, by the secondmobile edge platform, the API according to the identity ID of the radioaccess network device and/or the ID of the first mobile edge platform.

In some embodiments of the present invention, after the receiving, bythe second mobile edge platform, an API response sent by the firstmobile edge platform, the method includes: providing, by the secondmobile edge platform, the capability information for the second edgeservice server.

In some embodiments of the present invention, the receiving, by a secondmobile edge platform, registration information includes: receiving, bythe second mobile edge platform, the registration information sent bythe first mobile edge platform.

In some embodiments of the present invention, the receiving, by a secondmobile edge platform, registration information includes: receiving, bythe second mobile edge platform, the registration information sent by amanagement network element.

A third aspect of the present invention provides a mobile edge platform,where the mobile edge platform may include:

a processing module, configured to: obtain capability information of aradio access network device, configure an application programminginterface API, and set a use time limit of the API, where the API isused by the mobile edge platform to provide the capability informationfor a second mobile edge platform; and

a registration service module, configured to trigger a registrationfunction to send registration information to the second mobile edgeplatform, where the registration information includes an identifier ofthe API.

The processing module is further configured to: receive an API requestsent by the second mobile edge platform, where the API request includesthe identifier of the API, and the API request is used to request thecapability information from the mobile edge platform; detect whether theuse time limit of the API expires; and when detecting that the use timelimit of the API does not expire, send an API response to the secondmobile edge platform by using the API, where the API response includesthe capability information.

Optionally, the capability information includes a channel signal state,cell load, terminal location information, network congestion, and aterminal identity.

In some embodiments of the present invention, the processing module isfurther configured to: when detecting that the use time limit of the APIexpires, obtain current capability information of the radio accessnetwork device, where the current capability information is capabilityinformation of the radio access network device at a current time; andreset the use time limit of the API, and send, by using the API, an APIresponse including the current capability information to the secondmobile edge platform.

In some embodiments of the present invention, the registration servicemodule is specifically configured to send the registration informationto the second mobile edge platform.

In some embodiments of the present invention, the registration servicemodule is further specifically configured to trigger a managementnetwork element to send the registration information to the secondmobile edge platform by using the management network element.

In some embodiments of the present invention, the processing module isfurther configured to provide the capability information for a firstedge service server by using the API, where the first edge serviceserver and the mobile edge platform are disposed in a first Mobile EdgeComputing MEC server.

A fourth aspect of the present invention provides a mobile edgeplatform, where the mobile edge platform may include:

a registration service module, configured to receive registrationinformation, where the registration information includes an identifierof an application programming interface API, the API is used by a firstmobile edge platform to provide capability information for the mobileedge platform, and the capability information is capability informationof a radio access network device; and

a processing module, configured to: send an API request to the firstmobile edge platform, where the API request includes the identifier ofthe API, and the API request is used to request the capabilityinformation from the first mobile edge platform; and receive an APIresponse sent by the first mobile edge platform, where the API responseincludes the capability information.

Optionally, the capability information includes a channel signal state,cell load, terminal location information, network congestion, and aterminal identity.

In some embodiments of the present invention, the processing module isfurther configured to: before sending the API request to the firstmobile edge platform, receive a trigger request sent by a second edgeservice server, where the trigger request includes an identity ID of theradio access network device and/or an ID of the first mobile edgeplatform, the trigger request is used to trigger the mobile edgeplatform to send the API request to the first mobile edge platform, andthe second edge service server and the mobile edge platform are disposedin a second Mobile Edge Computing MEC server; and determine the APIaccording to the identity ID of the radio access network device and/orthe ID of the first mobile edge platform.

In some embodiments of the present invention, the processing module isfurther configured to: after receiving the API response sent by thefirst mobile edge platform, provide the capability information for thesecond edge service server.

In some embodiments of the present invention, the processing module isspecifically configured to receive the registration information sent bythe first mobile edge platform.

In some embodiments of the present invention, the processing module isspecifically configured to receive the registration information sent bya management network element.

A fifth aspect of the present invention provides an MEC server, wherethe MEC server may include the mobile edge platform provided in thethird aspect or the mobile edge platform provided in the fourth aspect.

In some embodiments of the present invention, the MEC server provided inthe fifth aspect may further include an edge service server, where themobile edge platform is further configured to provide capabilityinformation of a radio access network device for the edge serviceserver.

A sixth aspect of the present invention provides a capability exposureimplementation system, where the capability exposure implementationsystem may include a first mobile edge platform and a second mobile edgeplatform, where the first mobile edge platform is the mobile edgeplatform provided in the third aspect, and the second mobile edgeplatform is the mobile edge platform provided in the fourth aspect.

In some embodiments of the present invention, the capability exposureimplementation system provided in the sixth aspect further includes aradio access network device, where the radio access network device isconfigured to provide capability information for the first mobile edgeplatform.

In some embodiments of the present invention, the capability exposureimplementation system provided in the sixth aspect further includes aterminal, where the terminal is configured to provide a data packet (IPpacket).

A seventh aspect of the present invention further provides a capabilityexposure implementation system, where the capability exposureimplementation system may include a radio access network device, a firstMobile Edge Computing MEC server, and a second MEC server, where thefirst MEC server is the MEC server provided in the fifth aspect, thesecond MEC server is the MEC server provided in the fifth aspect, thefirst MEC server includes the mobile edge platform provided in the thirdaspect, and the second MEC server includes the mobile edge platformprovided in the fourth aspect.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of the presentinvention more clearly, the following briefly describes the accompanyingdrawings required for describing the embodiments. Apparently, theaccompanying drawings in the following description show merely someembodiments of the present invention, and a person of ordinary skill inthe art may still derive other drawings from these accompanying drawingswithout creative efforts.

FIG. 1 is a schematic diagram of an architecture of an MEC server in theprior art;

FIG. 2a is a schematic diagram of a deployment scenario of an MEC serverin the prior art;

FIG. 2b is a deployment scenario of cascading MEC servers according tosome embodiments of the present invention;

FIG. 2c is a schematic diagram of a communications interface forcommunication between an MEC server and a radio access network deviceaccording to an embodiment of the present invention;

FIG. 2d is a diagram of internal architectures of cascaded MEC serversdeployed based on FIG. 2b according to an embodiment of the presentinvention;

FIG. 2e is a diagram of an architecture of a capability exposureimplementation system according to an embodiment of the presentinvention;

FIG. 3A to FIG. 3C are a signaling diagram of a capability exposureimplementation method according to some embodiments of the presentinvention;

FIG. 4A to FIG. 4C are another signaling diagram of a capabilityexposure implementation method according to some embodiments of thepresent invention;

FIG. 5A to FIG. 5C are another signaling diagram of a capabilityexposure implementation method according to some embodiments of thepresent invention;

FIG. 6 is a schematic structural diagram of a mobile edge platformaccording to some embodiments of the present invention;

FIG. 7 is a schematic structural diagram of a mobile edge platformaccording to some other embodiments of the present invention;

FIG. 8 is a schematic structural diagram of an MEC server according tosome embodiments of the present invention;

FIG. 9 is a schematic structural diagram of an MEC server according tosome other embodiments of the present invention;

FIG. 10 is a schematic structural diagram of a capability exposureimplementation system according to some embodiments of the presentinvention;

FIG. 11 is a schematic structural diagram of a capability exposureimplementation system according to some other embodiments of the presentinvention; and

FIG. 12 is a schematic structural diagram of a capability exposureimplementation apparatus according to an embodiment of the presentinvention.

DESCRIPTION OF EMBODIMENTS

Embodiments of the present invention provide a capability exposureimplementation method, so as to implement deployment manners of cascadedMEC servers, that is, obtain capability information of a radio accessnetwork device, thereby reducing a delay, performing fast access, andimproving QoE, and further providing mobility support. The embodimentsof the present invention further provide a system, a mobile edgeplatform, and an MEC server that are corresponding to the capabilityexposure implementation method.

To make the invention objectives, features, and advantages of thepresent invention clearer and more comprehensible, the followingdescribes the technical solutions in the embodiments of the presentinvention with reference to the accompanying drawings in the embodimentsof the present invention. Apparently, the embodiments described aremerely a part rather than all of the embodiments of the presentinvention. All other embodiments obtained by a person of ordinary skillin the art based on the embodiments of the present invention withoutcreative efforts shall fall within the protection scope of the presentinvention.

In the specification, claims, and accompanying drawings of the presentinvention, the terms “first”, “second”, “third”, “fourth”, and so on areintended to distinguish between different objects but do not indicate aparticular order. In addition, the terms “including”, “including”, orany other variant thereof, are intended to cover a non-exclusiveinclusion. For example, a process, a method, a system, a product, or adevice that includes a series of steps or units is not limited to thelisted steps or units, but optionally further includes an unlisted stepor unit, or optionally further includes another inherent step or unit ofthe process, the method, the product, or the device.

A common deployment manner of an MEC server is first described.Referring to FIG. 2a , FIG. 2a is a schematic diagram of a deploymentscenario of an MEC server in the prior art. In FIG. 2a , the MEC servermay be deployed on a radio access network side according to manner 1,that is, disposed on an S1-U interface close to a radio access networkdevice. In FIG. 2a , that the radio access network device is an eNodeBis used as an example. In deployment manner 1, because the MEC serverhas a natural location advantage of being close to the radio accessnetwork device, the MEC server can obtain capability information of theradio access network device, so as to provide a localized innovationservice with a low delay, fast access, and high bandwidth.Alternatively, the MEC server may be deployed on a node between a radioaccess network and a core network according to manner 2, for example, aconvergence node of a convergence network in a 3G network. In deploymentmanner 2, the MEC server can support mobility of a base station.

However, in FIG. 2a , either deployment manner 1 or deployment manner 2exists, that is, the MEC server is deployed in deployment manner 1 orthe MEC server is deployed in deployment manner 2. Because a location ofthe MEC server is mainly considered during deployment, a deploymentmanner is relatively simple, flexibility is insufficient, and a functionof the MEC server cannot be fully used to implement service deploymentand improve an application scope of the MEC server.

Based on a defect of the deployment manner of the MEC server in theprior art, deployment of cascaded MEC servers is implemented in anembodiment of the present invention. The cascaded MEC servers includetwo or more levels of MEC servers (in this embodiment of the presentinvention, that the two levels of MEC servers are used to implement thecascaded MEC servers is used as example for description). Referring toFIG. 2b , FIG. 2b is a deployment scenario of cascading MEC serversaccording to some embodiments of the present invention. In FIG. 2b , anMEC server deployed on a radio access network device (a base station(eNodeB) is used as an example in FIG. 2b ) side is referred to as alow-layer MEC server (Low MEC), where the low-layer MEC server is afirst MEC server in an embodiment of the present invention, and an MECserver deployed at a high layer (that is, a node between a radio accessnetwork and a core network. That upper-layer nodes include a servinggateway (SGW) and a packet data network gateway (PGW) is used as anexample in FIG. 2b ) is referred to as a high-layer MEC server (HighMEC), where the high-layer MEC server is a second MEC server in anembodiment of the present invention. It is noted herein that thelow-layer MEC server and the high-layer MEC server are described insubsequent embodiments of the present invention.

It is further necessary to first describe herein an interface related tocommunication between an MEC server and a radio access network device.Referring to FIG. 2c , FIG. 2c is a schematic diagram of acommunications interface for communication between an MEC server and aradio access network device according to an embodiment of the presentinvention. In FIG. 2c , there are two function interfaces between theMEC server and the radio access network device: One type is a datainterface used to transmit data (an IP packet of UE) between the radioaccess network device and the MEC server; and the other type is asignaling interface used to transmit capability information between theradio access network device and the MEC server. The data interface isimplemented in two manners: One type is to use an external interface(that is, reset an interface for use), and the other type is to directlyuse an S1-U interface. The signaling interface is also implemented intwo manners: One type is to reuse the data interface (that is, the datainterface is used as both the data interface and the signalinginterface), and the other type is to use an external interface (that is,reset an interface).

With reference to FIG. 2c , when the high-layer MEC server is deployedin FIG. 2b , the low-layer MEC server may be deployed in two modesaccording to a location of the low-layer MEC server on a data plane: Thefirst type is an in-band mode (On-path model), that is, the low-layerMEC server exists, and the low-layer MEC server directly communicateswith the radio access network device by using the S1-U interface(transmits data by using the S1-U interface), where the IP packet maydirectly arrive at the high-layer MEC server after passing through thelow-layer MEC server; and the second type is an out-of-band mode(Off-path model), that is, the low-layer MEC server exists, but resetsthe interface to transmit data. Compared with the in-band mode, in theout-of-band mode, the IP packet needs to be uploaded to the base stationafter arriving at the low-layer MEC server, so as to continue to forwardthe IP packet to the high-layer MEC server.

In the in-band mode and the out-of-band mode shown in FIG. 2b ,capability information of the radio access network device can be exposedonly to the low-layer MEC server, and cannot be exposed to thehigh-layer MEC server. The high-layer MEC server can use the capabilityinformation of the radio access network device only by using thelow-layer MEC server (that is, the low-layer MEC server exposes thecapability information of the radio access network device to thehigh-layer MEC server). Therefore, this deployment manner is referred toas a manner of cascading MEC servers, and is one of layered deploymentmanners. This deployment manner not only delivers excellent performanceof deployment manner 1 and deployment manner 2 shown in FIG. 2a in theprior art, but also can reduce signaling information processed by theradio access network device, so as to reduce processing load of theradio access network device.

FIG. 2b shows only the deployment scenario in an EPS system. Thecascaded MEC servers provided in this embodiment of the presentinvention may be further applied to a 2G network system, a 3G networksystem, a 4G network system, a 5G network system, and a futurecommunications network. In the 2G network system, a low-layer MEC serverdisposed in a radio access network is close to a base station controller(BSC). In the 3G network system, a low-layer MEC server disposed in aradio access network is close to an RNC.

It is further noted that this embodiment of the present inventionfocuses on exposing the capability information of the radio accessnetwork device to the high-layer MEC server by using the low-layer MECserver, so that the capability information is exposed to an edge serviceserver of the high-layer MEC server for use.

Referring to FIG. 2d , FIG. 2d is a diagram of an internal architectureof an MEC server according to an embodiment of the present invention. InFIG. 2d , the MEC server mainly includes a mobile edge platform, arouting network, and an edge service server. The routing network isconfigured to forward data (such as an IP packet) or signaling (such asa request for capability information collection and feedback ofcapability information). The mobile edge platform provides services suchas a registration service, an RNIS, and a TOF service. The registrationservice, the RNIS, and the TOF service are dynamically generatedcapability information obtained from a radio access network device. Withreference to FIG. 2b , the MEC server that is provided in FIG. 2d andthat is deployed on an upper-layer node of a radio access network isused as a high-layer MEC server, and the MEC server that is provided inFIG. 2d and that is deployed on a radio access network side is used as alow-layer MEC server.

Referring to FIG. 2e , FIG. 2e is a diagram of an architecture of acapability exposure implementation system according to an embodiment ofthe present invention. In FIG. 2e , a mobile edge platform (a firstmobile edge platform in an embodiment of the present invention) of alow-layer MEC server requests capability information from a radio accessnetwork device by using a routing network, the routing network forwardsthe capability information to the mobile edge platform, the mobile edgeplatform provides the capability information for a mobile edge platform(a second mobile edge platform in an embodiment of the presentinvention) of a high-layer MEC server, and then the mobile edge platformof the high-layer MEC server provides the capability information for anedge service server (an edge service server of the high-layer MECserver).

A data packet (an IP packet, where the packet includes a service requestof a terminal, for example, a request for location positioning) sent bythe terminal arrives at the routing network of the low-layer MEC serverby using the radio access network device. If the low-layer MEC server isin the in-band mode, the routing network of the low-layer MEC serverdirectly forwards the data packet to a routing network of the high-layerMEC server, and then the routing network of the high-layer MEC serverforwards the data packet to the edge service server of the high-layerMEC server. If the low-layer MEC server is in the out-of-band mode, therouting network of the low-layer MEC server needs to upload the datapacket to the radio access network device, the radio access networkdevice sends the data packet to a routing network of the high-layer MECserver, and then the routing network of the high-layer MEC serverforwards the data packet to the edge service server of the high-layerMEC server.

It may be understood that this embodiment of the present inventionfocuses on how to use the low-layer MEC server to expose the capabilityinformation of the radio access network device to the high-layer MECserver, and an MEC platform of an MEC server obtains and exposes thecapability information. Therefore, when cascaded MEC servers areactually deployed, there is a special requirement for a location of amobile edge platform of the MEC server only, and a routing network andan edge service server may be located at other locations, that is, amobile edge platform needs to be deployed on a radio access network sideand a mobile edge platform needs to be deployed on an upper-layer nodeof a radio access network. Generally, cascaded mobile edge platforms areactually implemented. However, because mobile edge platforms belong todifferent MEC servers, it is equivalent to the fact that the cascadedMEC servers are deployed.

It should be noted that one high-layer MEC server may be correspondingto a plurality of low-layer MEC servers. In addition, in a low-layer MECserver, a mobile edge platform further provides capability informationfor an edge service server of the low-layer MEC server. However, thistechnology is the prior art, and is not described in detail herein.

The following describes in detail the technical solutions of the presentinvention by using specific embodiments.

Referring to FIG. 3A to FIG. 3C, FIG. 3A to FIG. 3C are a signalingdiagram of a capability exposure implementation method according to anembodiment of the present invention. As shown in FIG. 3A to FIG. 3C, thecapability exposure implementation method may include the followingsteps.

301. A first mobile edge platform sends a capability information requestto a radio access network device by using a first routing network.

The radio access network device includes an RNC, an eNodeB, a BSC, orthe like. The first mobile edge platform first sends the capabilityinformation request to the first routing network, and the first routingnetwork forwards the capability information request.

302. The radio access network device receives the capability informationrequest, and sends capability information to the first mobile edgeplatform by using the first routing network.

The capability information includes a channel signal state, cell load,terminal location information, network congestion, and a terminalidentity.

303. The first mobile edge platform receives the capability information,provides an API 1 that exposes the capability information to a secondmobile edge platform, and configures a use time limit of the API 1.

Because the first mobile edge platform has a location advantage of beingclose to the radio access network device, the first mobile edge platformcan obtain capability information of the radio access network devicefrom the radio access network device (that is, the radio access networkdevice exposes the capability information to the first mobile edgeplatform), and then stores the capability information. The first mobileedge platform provides the API 1 for the obtained capabilityinformation, and further exposes the capability information of the radioaccess network device to the second mobile edge platform by using theAPI 1. The second mobile edge platform may provide the capabilityinformation for a second edge service server.

Because the capability information of the radio access network devicemay also be updated, a use time limit of the API 1 needs to be set, thatis, the API 1 is invalid after a use time limit.

It may be further understood that both the capability informationrequest sent by the first mobile edge platform to the radio accessnetwork device and the capability information returned by the radioaccess network device are considered as signaling, and are transmittedon a signaling interface between the first routing network and the radioaccess network device.

304. The first mobile edge platform sends registration information tothe second mobile edge platform, where the registration informationincludes an identifier of the API 1, and an ID of the first mobile edgeplatform and/or an ID of the radio access network device.

It should be noted that, in this embodiment of the present invention,when cascaded MEC servers are deployed, an association relationshipbetween the first mobile edge platform, the second mobile edge platform,and the radio access network device is set on the second mobile edgeplatform. The registration information includes the identifier of theAPI 1, so as to notify the second mobile edge platform that thecapability information will be provided for the second edge serviceserver by using the API 1 later. Certainly, the registration informationmay further include the ID of the first mobile edge platform and/or theID of the radio access network device, so that the second mobile edgeplatform can clearly determine a to-be-invoked API 1 when the secondmobile edge platform needs to obtain the capability information from thefirst mobile edge platform.

The identifier of the API 1 may be a URL or a URI.

305. The second mobile edge platform receives the registrationinformation, provides an API 2, establishes a correspondence between theAPI 1 and the API 2, and exposes the API 2 to a second edge serviceserver.

It should be noted that after the second mobile edge platform receivesand stores the registration information, when a high-layer MEC server isenabled, the second edge service server initiates, to the second edgeplatform, a request for searching for the API 2, and then the secondedge platform feeds back information carrying an identifier of the API 2to the second edge service server.

306. A terminal sends an IP packet to the radio access network device.

307. The radio access network device forwards the IP packet to the firstrouting network.

The radio access network device sends the IP packet to the first routingnetwork by using a data interface.

308. The first routing network forwards the IP packet to a secondrouting network.

309. The second routing network forwards the IP packet to the secondedge service server.

310. The second edge service server obtains the ID of the radio accessnetwork device and/or the ID of the first mobile edge platform from thesecond mobile edge platform, and then determines the API 2.

It should be noted that, in this embodiment of the present invention, achannel used to transmit the IP packet carries the ID of the radioaccess network device, and the second mobile edge platform may obtain,according to a pre-configuration, the ID of the radio access networkdevice and/or the ID of the first mobile edge platform that are/iscorresponding to the IP packet, and then send the ID of the radio accessnetwork device and/or the ID of the first mobile edge platform to thesecond edge service server actively or when the second edge serviceserver makes a request.

311. The second edge service server sends an API 2 request to the secondmobile edge platform, where the API 2 request includes an identifier ofthe API 2, and the ID of the radio access network device and/or the IDof the first mobile edge platform.

The identifier of the API 2 may be a URL or a URI.

The API 2 request in this embodiment of the present invention is atrigger request provided in another embodiment, and is used to triggerthe second mobile edge platform to request the capability informationfrom the first mobile edge platform.

312. The second mobile edge platform determines the API 1 according tothe ID of the radio access network device and/or the ID of the firstmobile edge platform.

The second mobile edge platform determines, according to the ID of theradio access network device and/or the ID of the first mobile edgeplatform, the API 1 used to expose the capability information (becausethe registration information includes the ID of the first mobile edgeplatform or the ID of the radio access network device, and theidentifier of the API 1).

313. The second mobile edge platform sends an API 1 request to the firstmobile edge platform, where the API 1 request includes the identifier ofthe API 1.

314. The first mobile edge platform determines whether the use timelimit of the API 1 expires.

315. If the use time limit of the API 1 expires, the first mobile edgeplatform sends the capability information request to the radio accessnetwork device.

316. The radio access network device receives the capability informationrequest, and sends the capability information to the first mobile edgeplatform.

It should be noted that the capability information herein is currentcapability information of the radio access network device, and thecurrent capability information is latest capability information obtainedbefore the first mobile edge platform receives the current capabilityinformation, and may be the same as or different from the capabilityinformation obtained in step 301.

317. The first mobile edge platform receives the capability information,and resets the use time limit of the API 1.

318. If the use time limit of the API 1 does not expire, or afterre-obtaining current capability information from the radio accessnetwork device, the first mobile edge platform sends an API 1 responseto the second mobile edge platform, where the API 1 response includesthe capability information or the current capability information.

319. The second mobile edge platform receives the API 1 response, andthen obtains an API 2 response, where the API 2 response includes thecapability information included in the API 1 response.

It may be understood that the first mobile edge platform sends the API 1response to the second mobile edge platform by using the API 1, and thenthe second mobile edge platform sends the API 1 response to the secondedge service server by using the API 2.

320. The second mobile edge platform sends the API 2 response to thesecond edge service server.

321. After receiving the API 2 response, the second edge service serverprocesses the IP packet to obtain a fed-back IP packet.

322. The second edge service server sends the fed-back IP packet to thesecond routing network.

323. The second routing network sends the fed-back IP packet to thefirst routing network.

324. The first routing network forwards the fed-back IP packet to theradio access network device.

325. The radio access network device sends the fed-back IP packet to theterminal.

An in-band mode is mainly used in this embodiment of the presentinvention. In this embodiment, the first mobile edge platform exposesthe capability information of the radio access network device to thesecond mobile edge platform.

Further, in this embodiment of the present invention, the second mobileedge platform sends the API 1 request to the first mobile edge platformbecause the second edge service server receives the IP packet of theterminal, determines the API 2, obtains the ID of the radio accessnetwork device and/or the ID of the first mobile edge platform thatare/is corresponding to the IP packet from the second mobile edgeplatform, and then requests the capability information from the secondmobile edge platform. The first mobile edge platform obtains thecapability information of the radio access network device by using ageographical location advantage that the first mobile edge platform isclose to the radio access network device, and then the second mobileedge platform exposes the capability information to the second edgeservice server by using a geographical location advantage of the secondmobile edge platform, that is, may obtain the capability information ofthe radio access network device, so as to reduce a delay, perform fastaccess, improve QoE, and further provide mobility support.

The IP packet mentioned in all embodiments of the present inventionincludes a service request of the terminal, for example, the terminalrequests location positioning or requests a video. That the terminalrequests location positioning is used as an example. The terminalrequests location information from an edge service server of ahigh-layer MEC server by sending the IP packet. After receiving the IPpacket forwarded by the radio access network device and a low-layer MECserver, the edge service server obtains, by separately using an API 2interface and an API 1 interface according to a location positioningrequest requested in the IP packet, capability information required forpositioning a terminal location from a mobile edge platform of thelow-layer MEC server, for example, terminal location information.Finally, a mobile edge platform of the high-layer MEC server generatesthe IP packet according to the terminal location information, and feedsback the IP packet to the terminal.

Referring to FIG. 4A to FIG. 4C, FIG. 4A to FIG. 4C are anothersignaling diagram of a capability exposure implementation methodaccording to an embodiment of the present invention. As shown in FIG. 4Ato FIG. 4C, the capability exposure implementation method may includethe following steps.

Steps 401 to 407 are the same as steps 301 to 307, and are not describedin detail herein again.

408. The first routing network forwards the IP packet to the radioaccess network device.

409. The radio access network device forwards the IP packet to a secondrouting network.

Steps 410 to 426 are the same as steps 309 to 325, and are not describedin detail herein again.

An out-of-band mode is applied to this embodiment of the presentinvention. Therefore, in this embodiment of the present invention, arouting network of a low-layer MEC server cannot directly forward the IPpacket to a routing network of a high-layer MEC server, and the radioaccess network device needs to forward the IP packet to the routingnetwork of the high-layer MEC server.

It should be further noted that, in this embodiment of the presentinvention, the second mobile edge platform sends the API 1 request tothe first mobile edge platform because the second edge service serverreceives the IP packet of the terminal, obtains the ID of the firstmobile edge platform and/or the ID of the radio access network devicefrom the second mobile edge platform, then determines the API 2, andsends the API 2 request to the second mobile edge platform.

Referring to FIG. 5A to FIG. 5C, FIG. 5A to FIG. 5C are anothersignaling diagram of a capability exposure implementation methodaccording to an embodiment of the present invention. As shown in FIG. 5Ato FIG. 5C, the capability exposure implementation method may includethe following steps.

Steps 501 to 503 are the same as steps 301 to 303, and are not describedin detail herein again.

504. A management network element sends registration information to thesecond mobile edge platform.

In the embodiments shown in FIG. 3A to FIG. 3C and FIG. 4A to FIG. 4C,the mobile edge platform of the low-layer MEC server actively sends theregistration information to the mobile edge platform of the high-layerMEC server. In this embodiment of the present invention, a mobile edgeplatform of a low-layer MEC server triggers the management networkelement to send the registration information.

Step 505 is the same as step 305.

506. The second edge service server sends an API 2 request to the secondmobile edge platform.

It should be noted that, in the present invention, the second edgeservice server actively initiates the API 2 request instead of beingtriggered after receiving an IP packet of a terminal. The second edgeservice server may determine the API 2 according to a pre-configuredassociation relationship. The pre-configured association relationshipincludes an association relationship between the radio access networkdevice, the first mobile edge platform, and the second mobile edgeplatform, and further includes an association relationship between theAPI 2 and the API 1.

Steps 507 to 515 are the same as steps 312 to 320.

An in-band mode or an out-of-band mode may be applied to this embodimentof the present invention. In this embodiment of the present invention,the management network element sends the registration information, andthe management network element includes a mobile edge manager, a mobileedge orchestrator, and the like. However, an edge service server of ahigh-layer MEC server actively initiates the API 2 request withoutreceiving the IP packet, so as to request the capability information.When actively initiating the API 2 request, the high-layer MEC servermay obtain an ID of the radio access network device and/or an ID of thefirst mobile edge platform from a pre-configured file or from the secondmobile edge platform.

Referring to FIG. 6, FIG. 6 is a schematic structural diagram of amobile edge platform according to an embodiment of the presentinvention. As shown in FIG. 6, the mobile edge platform 600 may include:

a processing module 610, configured to: obtain capability information ofa radio access network device, configure an application programminginterface API, and set a use time limit of the API, where the API isused by the mobile edge platform to provide the capability informationfor a second mobile edge platform; and

a registration service module 620, configured to trigger a registrationfunction to send registration information to the second mobile edgeplatform, where the registration information includes an identifier ofthe API.

The processing module 610 is further configured to: receive an APIrequest sent by the second mobile edge platform, where the API requestincludes the identifier of the API, and the API request is used torequest the capability information from the mobile edge platform; detectwhether the use time limit of the API expires; and when detecting thatthe use time limit of the API does not expire, send an API response tothe second mobile edge platform by using the API, where the API responseincludes the capability information.

Optionally, the capability information includes a channel signal state,cell load, terminal location information, network congestion, and aterminal identity.

In some embodiments of the present invention, the processing module 610is further configured to: when detecting that the use time limit of theAPI expires, obtain current capability information of the radio accessnetwork device, where the current capability information is capabilityinformation of the radio access network device at a current time; andreset the use time limit of the API, and send, by using the API, an APIresponse including the current capability information to the secondmobile edge platform.

In some embodiments of the present invention, the registration servicemodule 620 is specifically configured to send the registrationinformation to the second mobile edge platform.

In some embodiments of the present invention, the registration servicemodule 620 is further specifically configured to trigger a managementnetwork element to send the registration information to the secondmobile edge platform by using the management network element.

In some embodiments of the present invention, the processing module 610is further configured to provide the capability information for a firstedge service server by using the API, where the first edge serviceserver and the mobile edge platform are disposed in a first Mobile EdgeComputing MEC server.

Referring to FIG. 7, FIG. 7 is another schematic structural diagram of amobile edge platform according to some embodiments of the presentinvention. As shown in FIG. 7, the mobile edge platform 700 may include:

a registration service module 710, configured to receive registrationinformation, where the registration information includes an identifierof an application programming interface API, the API is used by a firstmobile edge platform to provide capability information for the mobileedge platform, and the capability information is capability informationof a radio access network device; and

a processing module 720, configured to: send an API request to the firstmobile edge platform, where the API request includes the identifier ofthe API, and the API request is used to request the capabilityinformation from the first mobile edge platform; and receive an APIresponse sent by the first mobile edge platform, where the API responseincludes the capability information.

Optionally, the capability information includes a channel signal state,cell load, terminal location information, network congestion, and aterminal identity.

In some embodiments of the present invention, the processing module 720is further configured to: before sending the API request to the firstmobile edge platform, receive a trigger request sent by a second edgeservice server, where the trigger request includes an identity ID of theradio access network device and/or an ID of the first mobile edgeplatform, the trigger request is used to trigger the mobile edgeplatform to send the API request to the first mobile edge platform, andthe second edge service server and the mobile edge platform are disposedin a second Mobile Edge Computing MEC server; and determine the APIaccording to the identity ID of the radio access network device and/orthe ID of the first mobile edge platform.

In some embodiments of the present invention, the processing module 720is further configured to: after receiving the API response sent by thefirst mobile edge platform, provide the capability information for thesecond edge service server.

In some embodiments of the present invention, the processing module 720is specifically configured to receive the registration information sentby the first mobile edge platform.

In some embodiments of the present invention, the processing module 720is specifically configured to receive the registration information sentby a management network element.

Referring to FIG. 8, FIG. 8 is a schematic structural diagram of an MECserver according to an embodiment of the present invention. As shown inFIG. 8, the MEC server 800 includes the mobile edge platform 600.

The mobile edge platform 600 is the first mobile edge platform describedin this embodiment of the present invention.

Further, the MEC server 800 includes an edge service server 810, forexample, the first edge service server described above.

Further, the MEC server 800 includes a routing network 820. The routingnetwork 820 is specifically the first routing network provided in thisembodiment of the present invention.

Referring to FIG. 9, FIG. 9 is a schematic structural diagram of an MECserver according to some other embodiments of the present invention. Asshown in FIG. 9, the MEC server 900 includes the mobile edge platform700.

The mobile edge platform 700 is the second mobile edge platformdescribed in this embodiment of the present invention.

Further, the MEC server 900 includes an edge service server 910, forexample, the second edge service server described above.

Further, the MEC server 900 includes a routing network 920. The routingnetwork 920 is specifically the second routing network provided in thisembodiment of the present invention.

Referring to FIG. 10, FIG. 10 is a schematic structural diagram of acapability exposure implementation system according to an embodiment ofthe present invention. As shown in FIG. 10, the capability exposureimplementation system 1000 may include:

the mobile edge platform 600 shown in FIG. 6 and the mobile edgeplatform 700 shown in FIG. 7.

Further, the capability exposure implementation system 1000 includes aradio access network device 1010. The radio access network device 1010is configured to provide capability information to the first mobile edgeplatform.

Still further, the capability exposure implementation system 1000includes a terminal 1020. For specific content of the terminal 1020,refer to a description of the foregoing method embodiment.

Referring to FIG. 11, FIG. 11 is a schematic structural diagram of acapability exposure implementation system according to an embodiment ofthe present invention. As shown in FIG. 11, the capability exposureimplementation system 1100 may include:

the MEC server 800 shown in FIG. 8, the MEC server 900 shown in FIG. 9,and a radio access network device 1110.

Further, the capability exposure implementation system 1100 includes aterminal 1120. For specific content, refer to a description of theforegoing method embodiment.

Referring to FIG. 12, FIG. 12 is a schematic structural diagram of acapability exposure implementation apparatus according to an embodimentof the present invention. The capability exposure implementationapparatus may include at least one processor 1201 (for example, a CPU,Central Processing Unit), at least one network interface or anothercommunications interface, a memory 1202, and at least one communicationsbus that is configured to implement connection and communication betweenthese apparatuses. The processor 1201 is configured to execute anexecutable module stored in the memory, for example, a computer program.The memory 1202 may include a high-speed random access memory (RAM), ormay include a non-volatile memory (non-volatile memory), for example, atleast one magnetic disk memory. The at least one network interface(which may be wired or wireless) is used to implement a communicationsconnection between a system gateway and at least one another networkelement by using the Internet, a wide area network, a local areanetwork, a metropolitan area network, or the like.

As shown in FIG. 12, in some implementations, the memory 1202 stores aprogram instruction, where the program instruction may be executed bythe processor 1201. The processor 1201 specifically performs thefollowing steps: obtaining capability information of a radio accessnetwork device, configuring an application programming interface API,and setting a use time limit of the API, where the API is used by amobile edge platform to provide the capability information for a secondmobile edge platform; triggering a registration function to sendregistration information to the second mobile edge platform, where theregistration information includes an identifier of the API; receiving anAPI request sent by the second mobile edge platform, where the APIrequest includes the identifier of the API, and the API request is usedto request the capability information from the mobile edge platform;detecting whether the use time limit of the API expires; and whendetecting that the use time limit of the API does not expire, sending anAPI response to the second mobile edge platform by using the API, wherethe API response includes the capability information.

Alternatively, the processor 1201 specifically performs the followingsteps: receiving registration information, where the registrationinformation includes an identifier of an application programminginterface API, the API is used by a first mobile edge platform toprovide capability information for the mobile edge platform, and thecapability information is capability information of a radio accessnetwork device; sending an API request to the first mobile edgeplatform, where the API request includes the identifier of the API, andthe API request is used to request the capability information from thefirst mobile edge platform; and receiving an API response sent by thefirst mobile edge platform, where the API response includes thecapability information.

In some implementations, the processor 1201 may further perform thefollowing steps: when detecting that the use time limit of the APIexpires, obtaining current capability information of the radio accessnetwork device, where the current capability information is capabilityinformation of the radio access network device at a current time; andresetting the use time limit of the API, and sending, by using the API,an API response including the current capability information to thesecond mobile edge platform.

In some implementations, the processor 1201 may further perform thefollowing step: sending the registration information to the secondmobile edge platform.

In some implementations, the processor 1201 may further perform thefollowing step: triggering a management network element to send theregistration information to the second mobile edge platform by using themanagement network element.

In some implementations, the processor 1201 may further perform thefollowing step: providing the capability information for a first edgeservice server by using the API, where the first edge service server andthe mobile edge platform are disposed in a first Mobile Edge ComputingMEC server.

In some implementations, the processor 1201 may further perform thefollowing steps: before sending the API request to the first mobile edgeplatform, receiving a trigger request sent by a second edge serviceserver, where the trigger request includes an identity ID of the radioaccess network device and/or an ID of the first mobile edge platform,the trigger request is used to trigger the mobile edge platform to sendthe API request to the first mobile edge platform, and the second edgeservice server and the mobile edge platform are disposed in a secondMobile Edge Computing MEC server; and determining the API according tothe identity ID of the radio access network device and/or the ID of thefirst mobile edge platform.

In some implementations, the processor 1201 may further perform thefollowing step: after receiving the API response sent by the firstmobile edge platform, providing the capability information for thesecond edge service server.

In some implementations, the processor 1201 may further perform thefollowing step: receiving the registration information sent by the firstmobile edge platform.

In some implementations, the processor 1201 may further perform thefollowing step: receiving the registration information sent by amanagement network element.

In the foregoing embodiments, the description of each embodiment hasrespective focuses. For a part that is not described in detail in anembodiment, reference may be made to related descriptions in otherembodiments.

It may be clearly understood by a person skilled in the art that, forthe purpose of convenient and brief description, for a detailed workingprocess of the foregoing system, apparatus, and unit, reference may bemade to a corresponding process in the foregoing method embodiments, anddetails are not described herein again.

In the several embodiments provided in this application, it should beunderstood that the disclosed system, apparatus, and method may beimplemented in other manners. For example, the described apparatusembodiment is merely an example. For example, the unit division ismerely logical function division and may be other division in actualimplementation. For example, a plurality of units or components may becombined or integrated into another system, or some features may beignored or not performed. In addition, the displayed or discussed mutualcouplings or direct couplings or communication connections may beimplemented by using some interfaces. The indirect couplings orcommunication connections between the apparatuses or units may beimplemented in electronic, mechanical, or other forms.

The units described as separate parts may or may not be physicallyseparate, and parts displayed as units may or may not be physical units,may be located in one position, or may be distributed on a plurality ofnetwork units. Some or all of the units may be selected according toactual requirements to achieve the objectives of the solutions of theembodiments.

In addition, function units in the embodiments of the present inventionmay be integrated into one processing unit, or each of the units mayexist alone physically, or two or more units are integrated into oneunit. The integrated unit may be implemented in a form of hardware, ormay be implemented in a form of a software function unit.

When the integrated unit is implemented in the form of a softwarefunction unit and sold or used as an independent product, the integratedunit may be stored in a computer-readable storage medium. Based on suchan understanding, the technical solutions of the present inventionessentially, or the part contributing to the prior art, or all or someof the technical solutions may be implemented in the form of a softwareproduct. The software product is stored in a storage medium and includesseveral instructions for instructing a computer device (which may be apersonal computer, a server, or a network device) to perform all or someof the steps of the methods described in the embodiments of the presentinvention. The foregoing storage medium includes: any medium that canstore program code, such as a USB flash drive, a removable hard disk, aread-only memory (ROM), a random access memory (RAM), a magnetic disk,or an optical disc.

The foregoing describes in detail the capability exposure implementationmethod and system, and the related device provided in the presentinvention. A person of ordinary skill in the art may make modificationswith respect to a specific implementation and an application scopeaccording to the ideas of the embodiments of the present invention. Inconclusion, content of this specification shall not be construed as alimitation on the present invention.

What is claimed is:
 1. A capability exposure implementation method,comprising: obtaining, by a first mobile edge platform, capabilityinformation of a radio access network device; configuring an applicationprogramming interface (API); setting a use time limit of the API,wherein the API is used by the first mobile edge platform to provide thecapability information for a second mobile edge platform; triggering, bythe first mobile edge platform, a registration function to sendregistration information to the second mobile edge platform, wherein theregistration information comprises an identifier of the API; receiving,by the first mobile edge platform, an API request from the second mobileedge platform, wherein the API request comprises the identifier of theAPI, and the API request is used to request the capability informationfrom the first mobile edge platform; detecting, by the first mobile edgeplatform, whether the use time limit of the API expires; and when theuse time limit of the API does not expire, sending, by the first mobileedge platform, an API response to the second mobile edge platform byusing the API, wherein the API response comprises the capabilityinformation.
 2. The method according to claim 1, wherein the methodfurther comprises: when the use time limit of the API expires,obtaining, by the first mobile edge platform, current capabilityinformation of the radio access network device, wherein the currentcapability information is capability information of the radio accessnetwork device at a current time; resetting, by the first mobile edgeplatform, the use time limit of the API; and sending, by using the API,an API response comprising the current capability information to thesecond mobile edge platform.
 3. The method according to claim 1, whereinthe triggering, by the first mobile edge platform, the registrationfunction to send registration information to the second mobile edgeplatform comprises: sending, by the first mobile edge platform, theregistration information to the second mobile edge platform.
 4. Themethod according to claim 1, wherein the triggering, by the first mobileedge platform, the registration function to send registrationinformation to the second mobile edge platform comprises: triggering, bythe first mobile edge platform, a management network element to send theregistration information to the second mobile edge platform by using themanagement network element.
 5. The method according to claim 1, whereinthe method further comprises: providing, by the first mobile edgeplatform, the capability information for a first edge service server byusing the API, wherein the first edge service server and the firstmobile edge platform are disposed in a first Mobile Edge Computing (MEC)server.
 6. The method according to claim 1, wherein the capabilityinformation comprises at least one of a channel signal state, cell load,terminal location information, network congestion, or a terminalidentity.
 7. A capability exposure implementation method, comprising:receiving, by a second mobile edge platform, registration information,wherein the registration information comprises an identifier of anapplication programming interface (API), the API is used by a firstmobile edge platform to provide capability information for the secondmobile edge platform, and the capability information is capabilityinformation of a radio access network device; sending, by the secondmobile edge platform, an API request to the first mobile edge platform,wherein the API request comprises the identifier of the API, and the APIrequest is used to request the capability information from the firstmobile edge platform; and receiving, by the second mobile edge platform,an API response from the first mobile edge platform, wherein the APIresponse comprises the capability information.
 8. The method accordingto claim 7, wherein before the sending, by the second mobile edgeplatform, the API request to the first mobile edge platform, the methodcomprises: receiving, by the second mobile edge platform, a triggerrequest from a second edge service server, wherein the trigger requestcomprises at least one of an identity (ID) of the radio access networkdevice or an ID of the first mobile edge platform, the trigger requestis used to trigger the second mobile edge platform to send the APIrequest to the first mobile edge platform, and the second edge serviceserver and the second mobile edge platform are disposed in a secondMobile Edge Computing (MEC) server; and determining, by the secondmobile edge platform, the API according to the at least one of the ID ofthe radio access network device or the ID of the first mobile edgeplatform.
 9. The method according to claim 8, wherein after thereceiving, by the second mobile edge platform, the API response from thefirst mobile edge platform, the method comprises: providing, by thesecond mobile edge platform, the capability information for the secondedge service server.
 10. The method according to claim 7, wherein thereceiving, by the second mobile edge platform, registration informationcomprises: receiving, by the second mobile edge platform, theregistration information from the first mobile edge platform.
 11. Themethod according to claim 7, wherein the receiving, by the second mobileedge platform, registration information comprises: receiving, by thesecond mobile edge platform, the registration information from amanagement network element.
 12. The method according to claim 7, whereinthe capability information comprises at least one of a channel signalstate, cell load, terminal location information, network congestion, ora terminal identity.
 13. A mobile edge platform, comprising: at leastone processor; and a memory, wherein the memory stores a programinstruction, and the at least one processor is configured to execute theprogram instruction stored in the memory to perform the following steps:obtaining capability information of a radio access network device;configuring an application programming interface API; set a use timelimit of the API, wherein the API is used by the mobile edge platform toprovide the capability information for a second mobile edge platform;triggering a registration function to send registration information tothe second mobile edge platform, wherein the registration informationcomprises an identifier of the API; receiving an API request from thesecond mobile edge platform, wherein the API request comprises theidentifier of the API, and the API request is used to request thecapability information from the mobile edge platform; detecting whetherthe use time limit of the API expires; and when detecting that the usetime limit of the API does not expire, sending an API response to thesecond mobile edge platform by using the API, wherein the API responsecomprises the capability information.
 14. The mobile edge platformaccording to claim 13, wherein the steps further comprises: whendetecting that the use time limit of the API expires, obtaining currentcapability information of the radio access network device, wherein thecurrent capability information is capability information of the radioaccess network device at a current time; resetting the use time limit ofthe API; and sending, by using the API, an API response comprising thecurrent capability information to the second mobile edge platform. 15.The mobile edge platform according to claim 13, wherein the stepsfurther comprises: sending the registration information to the secondmobile edge platform; or triggering a management network element to sendthe registration information to the second mobile edge platform by usingthe management network element.
 16. The mobile edge platform accordingto claim 13, wherein the steps further comprises: providing thecapability information for a first edge service server by using the API,wherein the first edge service server and the mobile edge platform aredisposed in a first Mobile Edge Computing (MEC) server.
 17. A mobileedge platform, comprising: at least one processor; and a memory, whereinthe memory stores a program instruction, and the at least one processoris configured to execute the program instruction stored in the memory toperform the following steps: receiving registration information, whereinthe registration information comprises an identifier of an applicationprogramming interface (API), the API is used by a first mobile edgeplatform to provide capability information for the mobile edge platform,and the capability information is capability information of a radioaccess network device; sending an API request to the first mobile edgeplatform, wherein the API request comprises the identifier of the API,and the API request is used to request the capability information fromthe first mobile edge platform; and receiving an API response from thefirst mobile edge platform, wherein the API response comprises thecapability information.
 18. The mobile edge platform according to claim17, wherein the steps further comprises: before sending the API requestto the first mobile edge platform, receiving a trigger request from asecond edge service server, wherein the trigger request comprises atleast one of an identity (ID) of the radio access network device or anID of the first mobile edge platform, the trigger request is used totrigger the mobile edge platform to send the API request to the firstmobile edge platform, and the second edge service server and the mobileedge platform are disposed in a second Mobile Edge Computing (MEC)server; and determining the API according to the at least one of the IDof the radio access network device or the ID of the first mobile edgeplatform.
 19. The mobile edge platform according to claim 18, whereinthe steps further comprises: after receiving the API response from thefirst mobile edge platform, providing the capability information for thesecond edge service server.
 20. The mobile edge platform according toclaim 17, wherein the steps further comprises: receiving theregistration information from the first mobile edge platform; orreceiving the registration information from a management networkelement.